Thank you so much for this PR! Would you be able to verify the change to extract-translations-source-files is working on your fork? If you have actions enabled on your fork you should be able to visit https://github.com/nsprenkle/openedx-translations/actions/workflows/extract-translation-source-files.yml and see a workflow_dispatch trigger

Thank you so much for this PR! Would you be able to verify the change to extract-translations-source-files is working on your fork? If you have actions enabled on your fork you should be able to visit https://github.com/nsprenkle/openedx-translations/actions/workflows/extract-translation-source-files.yml and see a workflow_dispatch trigger

Hey @brian-smith-tcril , none of the workflows here transferred over to my fork. Is there a standard process to get these set up?

Okay, @brian-smith-tcril , I did a bit of research and troubleshooting but figured it out. Capturing what I found here for folks who may run into something similar.

1. GitHub actions (by default) only run on main/`master. I had to merge my changes into main to get the workflows to show up.
2. I had to modify the .github/workflows/extract-translation-source-files.yml file (see nsprenkle@67d4a9e) to get the runner to pick up from the openedx org instead of my personal account.

After those, I was then able to ✅ successfully run the workflow creating these files on this new branch .

My question: is success in running that job all that is needed for verification?

Thank you so much for writing up the changes you needed to make to verify it on your fork! It looks like the generated file is valid and the path matches the one you added to transifex.yml so this should be good to go!

Excellent, thanks for checking back in, @brian-smith-tcril.

I'm unable to merge so are you able to merge this PR?